In `@docs/majutsu.org`:
- Around line 135-138: Update the docs text to clarify that the claim "C-j /
C-<return> always visit the workspace file" is not true when Evil mode remaps
C-j: mention Evil specifically and state that C-j may be overridden by Evil's
section navigation, recommend using C-<return> (which is unaffected) or provide
the alternative keybinding (e.g., bind a different key or instruct users to
unmap/remap Evil's C-j) and include the terms "C-j", "C-<return>", and "Evil" so
readers can locate the related sentence.

In `@majutsu-diff.el`:
- Around line 865-869: majutsu-find-file is calling majutsu-find-file--display
and expecting a buffer, but majutsu-find-file--display currently just calls
(funcall display-fn buffer) and doesn't return the buffer; update
majutsu-find-file--display to explicitly return the buffer (e.g., call the
display function but ensure the function returns the buffer value) so callers
like majutsu-diff--goto-line-col receive a non-nil buf; touch
majutsu-find-file--display and ensure its return value is the buffer after
invoking display-fn.

In `@majutsu-file.el`:
- Around line 286-303: The log calls in majutsu-file-prev-change and
majutsu-file-next-change use the -G graph flag which can inject graph characters
into the output and confuse parsing of the change_id; update the
majutsu-jj-string invocations inside majutsu-file-prev-change and
majutsu-file-next-change to include the --no-graph option (or remove -G) so the
output is plain change_id like in majutsu-file--resolve-single-rev, ensuring the
parsed result is the raw change id.
- Line 27: The declare-function for majutsu-bury-or-kill-buffer is referencing a
symbol that isn't defined, causing majutsu-blob-quit to call an undefined
function; fix by either adding a proper definition for
majutsu-bury-or-kill-buffer in this file (implement the bury-or-kill behavior
expected by majutsu-blob-quit) or update the declare-function to point to the
correct file that actually provides the function name (or change calls in
majutsu-blob-quit to the real function name); locate the usage in
majutsu-blob-quit and the declaration line to ensure the symbol and its provider
file match.
- Around line 229-237: The revset builder uses single-quoted revset strings and
only escapes single quotes, which fails for filenames with apostrophes; update
majutsu-file--revset-for-files to produce double-quoted revset strings and
properly escape backslashes and double quotes in the path: change the escaped
computation to escape backslashes and double quotes (e.g. replace "\\" with
"\\\\" then "\"" with "\\\"" or equivalent), change file-set from "files('%s')"
to "files(\"%s\")", and keep the existing uses of file-set in the ('prev and
'next) format calls so revset generation uses the safe double-quoted path.

In `@majutsu-base.el`:
- Around line 287-296: The regexp used in the jj-revision thing-at-point helpers
only matches letters ("[a-z]\{1,12\}") so hex commit IDs with digits aren't
recognized; update the looking-at pattern inside the bounds-of-thing-at-point
lambda (the put 'jj-revision 'bounds-of-thing-at-point entry) to include digits,
e.g. change "[a-z]\\{1,12\\}" to "[0-9a-z]\\{1,12\\}" so both
bounds-of-thing-at-point and the dependent thing-at-point lambda will correctly
detect commit IDs.

In `@majutsu-file.el`:
- Around line 80-83: Both jj invocations must terminate options to avoid
treating paths beginning with '-' as flags: update majutsu-file--show to call
majutsu-jj-string with "file" "show" "-r" revset "--" path, and update
majutsu-file--list to include a "--" after "list" (e.g. "file" "list" "--") so
future/positional arguments won't be parsed as options; keep
majutsu-file--map-line unchanged since it already uses "--".

In `@majutsu-diff.el`:
- Around line 811-825: The function majutsu-diff--visit-workspace-p fails to
treat a diff with only --from as visiting the workspace; update it so when
majutsu-buffer-diff-range yields a non-nil revisions value but the computed to
value is nil, it returns t (i.e., treat --from=X with no explicit --to as
--to=@). Locate majutsu-diff--visit-workspace-p and adjust the cond (using
majutsu-diff--range-value, majutsu-buffer-diff-range, and the local vars to and
revisions) to include a clause like (and revisions (null to)) that returns t
before the final fallback.
- Around line 761-772: majutsu-diff--default-revset should return the parent
revset "@-" when the current diff buffer indicates we're on a removed line;
update the logic in majutsu-diff--default-revset to detect removed lines via
majutsu-diff--on-removed-line-p and, when removed and no explicit
--revisions/--from/--to provide a usable revset, return "@-" instead of falling
through to the default "@". Ensure the existing checks for (revisions revisions)
and (from ...) remain, but change the final fallback branch that currently
returns "@" to return "@-" when (majutsu-diff--on-removed-line-p) is true,
otherwise keep "@".

In `@majutsu-file.el`:
- Around line 92-97: The call to majutsu-diff--file-at-point inside
majutsu-file--path-at-point can raise a void-function error when the diff module
isn't loaded; guard that call with a feature check (use (fboundp
'majutsu-diff--file-at-point)) and only invoke majutsu-diff--file-at-point when
that check passes, and optionally add a declare-function for
majutsu-diff--file-at-point at top of file to satisfy byte-compiler warnings.
Ensure the or expression uses the guarded conditional in place of the direct
call so majutsu-file--path-at-point never calls an undefined function.
- Around line 224-233: The function majutsu-blob-visit-file currently calls
find-file on the expanded path which will create a new file if the blob's file
was deleted; change majutsu-blob-visit-file to compute the target path (using
expand-file-name on majutsu-buffer-blob-path and majutsu-buffer-blob-root),
check it with file-exists-p, and call find-file only if the file exists
otherwise raise a user-error with a clear message indicating the workspace file
was not found.

In `@majutsu-file.el`:
- Around line 185-190: majutsu-find-file--display currently calls (funcall
display-fn buffer) but does not return the buffer, causing callers like
majutsu-diff-visit-file to receive nil; modify majutsu-find-file--display (which
computes root, path, buffer and calls display-fn) so it returns the buffer
(e.g., call display-fn for side-effects then ensure the function returns buffer)
so callers receive the buffer they expect.

In `@majutsu-base.el`:
- Around line 266-286: majutsu-change-at-point fails to extract a revision from
majutsu-buffer-diff-range because that variable is a list of strings and (cdr
(assoc "--revisions=" range)) always returns nil; update the derived-mode branch
in majutsu-change-at-point to search the list for an element whose string starts
with "--revisions=", and if found return the substring after the '=' (or split
on '=' and return the second part). Reference: majutsu-change-at-point,
majutsu-buffer-diff-range, and the literal "--revisions=" string.

In `@majutsu-evil.el`:
- Around line 85-99: The current unbinding in
majutsu-evil--adjust-section-bindings runs only if the section keymap symbols
already exist, so C-j may be rebound when those majutsu files load later; change
the setup to defer unbinding by adding with-eval-after-load handlers (or a
majutsu-mode hook) that run the define-key nil for each map when its defining
feature/file loads. Concretely, keep majutsu-evil--adjust-section-bindings as
the unbind logic but call it inside with-eval-after-load blocks for the features
that create majutsu-diff-section-map, majutsu-file-section-map and
majutsu-hunk-section-map (or register it on majutsu-mode-hook) so the C-j keys
are removed even if the maps are defined after Evil setup.

In `@majutsu-file.el`:
- Around line 113-125: The fallback revset in majutsu-file--diff-revset returns
"@" for lines with no explicit range; change the final fallback to return "@-"
for removed lines. Update the final cond clause in majutsu-file--diff-revset
(currently (t "@")) to check the local removed variable and return (if removed
"@-" "@") so removed lines resolve to the parent revision.

In `@majutsu-file.el`:
- Around line 235-243: The revset builder majutsu-file--revset-for-files
currently only escapes double quotes, so backslashes in PATH will be
misinterpreted; update the escaping step (the call to replace-regexp-in-string)
to first replace backslashes with escaped backslashes, then escape double quotes
(i.e., run a replacement that turns "\" into "\\\""" in Elisp string literal
terms), ensuring you perform backslash escaping before quote escaping so the
produced file-set string is valid for jj's double-quoted syntax.

In `@majutsu-file.el`:
- Around line 246-276: majutsu-file--diff-offset misses processing '+' lines
that occur immediately after the last consumed old line because the inner while
stops when rest reaches 0 and returns without scanning any subsequent added
lines; fix by, after the inner while that consumes 'rest', continuing to scan
successive hunk lines at point and applying any leading '+' lines to offset
(increment offset for each '+' line and forward-line 1) until you hit a context
or deletion line, ensuring you still use the same cursor/char-after/forward-line
logic and update offset accordingly (keep existing behavior for handling ?\s and
?- inside the inner loop and then add the extra loop to handle trailing '+'s
when rest becomes 0).